Fix: Bind Next.js to 0.0.0.0 instead of localhost#32
Merged
Conversation
BigSimmo
added a commit
that referenced
this pull request
Jul 22, 2026
Co-authored-by: Cursor <cursoragent@cursor.com>
2 tasks
BigSimmo
added a commit
that referenced
this pull request
Jul 22, 2026
Co-authored-by: Cursor <cursoragent@cursor.com>
BigSimmo
added a commit
that referenced
this pull request
Jul 22, 2026
Co-authored-by: Cursor <cursoragent@cursor.com>
3 tasks
BigSimmo
added a commit
that referenced
this pull request
Jul 25, 2026
cursor Bot
pushed a commit
that referenced
this pull request
Jul 25, 2026
* docs: close ledger #9 #10 #32 #41 #63 Record ops-only /api/jobs decision, coming-soon audit, governance ranking REFUTED guardrail, Factsheets reading-model brief, and Current Clinical Work privacy/persistence brief. Archive the five open items; no RAG or application behavior changes. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * fix(ci): prettier ledger docs and drop stale PR_POLICY_BODY Static PR checks failed on Prettier for five docs files. Also remove leftover PR_POLICY_BODY.md from merged #1134 so Sync PR policy body stops overwriting this docs PR description. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * docs: record PR #1175 review ledger outcome Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * chore: restore PR #1175 description via PR_POLICY_BODY sync Temporary template so CI Sync PR policy body replaces the polluted search-performance description left from merged #1134. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * chore: remove temporary PR_POLICY_BODY after description sync Keep the corrected PR #1175 description without leaving the sync template on the branch for merge to main. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * docs: supersede PR #1175 review ledger after body sync Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * style: prettier-format outstanding-issues after ledger merge --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Next.js app was spawned with
--hostname localhost, binding it to 127.0.0.1 only. Railway's healthcheck probe connects from outside the container, so it could never reach the app, causing every deployment to fail.Solution
Changed the
--hostnameargument inscripts/dev-free-port.mjsfrom"localhost"to"0.0.0.0", so Next.js listens on all network interfaces. This allows Railway's healthcheck and external traffic to reach the app.Changes
scripts/dev-free-port.mjsGenerated by Railway